ShowTable of Contents
Overview
When multiple users share the same workstation, the configuration is referred to as a multiuser installation. This means that a single Expeditor client exists and is shared among all users; however, each user has their own workspace containing configuration details specific to that user. As administrators install new client features, other users may report that the feature does not work within their client. Administrators should make specific accommodations to ensure that features within a multiuser installation are enabled for all users.
Checking Feature Enablement
To verify that a feature is disabled, access the File -> Application -> Application Management action. For demonstration purposes, the Log Viewer feature has been disabled (highlighted in blue). Notice the icon is different than other enabled features. To view disabled features, you must toggle the "Show Disabled Features" button (highlighted in red). It's often the case that administrators do not see any disabled features because by default this button is in the disabled state.
Enabling Features for All Users
To ensure that a feature not only installs but also enables for all users, deployers should make the following changes to the feature to be installed.
Create an Install Manifest
Within the feature, create an install.xml file. The contents of a file are detailed below.
<?xml version="1.0" encoding="UTF-8"?>
<ibm-portal-composite>
<domain-object name="com.ibm.rcp.installmanifest">
<object-data>
<install>
<installfeature>
<requirements>
<feature action="install" id="com.ibm.rcp.support.multiuser.feature"
match="compatible" shared="true" version="6.2.2" config="multiuser"/>
</requirements>
</installfeature>
</install>
</object-data>
</domain-object>
</ibm-portal-composite>
The ID and version attribute are specific to the feature; all other attributes are boilerplate.
Create a Feature Handler
Create another file, handler.properties. The contents of this file contain the mergemanifest provisioning action.
mergemanifest=${features.dir}/com.ibm.rcp.support.multiuser.feature_6.2.2/install.xml
Again, the value com.ibm.rcp.support.multiuser.feature_6.2.2 should be adjusted to be specific to your feature. This is simply the directory name found in the features directory - the feature ID appended with an underscore and the version.
Update the Build File
Since new files have been added to the project, ensure that they are deployed with the feature. Do this by ensuring the new files are listed and checked in the Build tab of the plugin editor.
Add a Feature Installation Handler
Finally, ensure that the com.ibm.rcp.installhandler.RCPInstallHandler class is listed on the Installation tab of the plugin editor. This ensures that the handler.properties file previously created is processed during feature installation.
